Is there a trigger on deletion of objects in a module?

Mathias Mamsch - Tue Dec 29 12:58:25 EST 2009
As far as I know there is no reliable way to hook object creation, object deletion or link creation/deletion. It seems that Telelogic wanted to implement them but they probably never found the time since Version 7 or earlier.
There are ways to use the "Sync" event trigger or the "Close module" event trigger on a and look at the history but all the ways I tried so far are not 100% reliable.

Regards, Mathias

roybond - Fri Jan 08 03:08:46 EST 2010
You CAN get DOORS to reacte to the deletion of an Object, if you have deleted Objects visible in the View (by setting 'View','Show','Deletions' in the Formal Module menu).

I have a DXL Attribute which simply contains "isDeleted(obj)" which is then set TRUE when a user hits the Delete Key on the current Object, which in turn fires a Trigger.

In my case, I use the Trigger to then undelete the Object, and then set a Status Attribute to "DELETED" (which is only one of the possible enumerations, eg. DRAFT, REVIEW, etc.)

In this way, I can then more accurately (and easily) report on the status of all Objects in the Module.

Have fun,

Roy.

email: roy.bond@baesystems.com

SudarshanRao - Mon Jan 04 09:53:54 EST 2010
I guess the best option is to first loop through the history sessions to identify the last session and then check for history records in that last session for HistoryType deleteObject/purgeObject..

For eg.,
==================================
HistorySession hs
History h
int sessNo, lastNo

for hs in current Module do
{}
lastNo = number hs
lastNo++
for h in current Module do
{
sessNo = h.sessionNo
if(sessNo == lastNo)
{
print h.author "\t" h.date "\t" h.type "\n"
//Do the manipulation with h.type here..
}
}
print "Done"
==================================

But with growing history, this would hit on performance..

cheers,
Sudarshan

cidem - Fri Jan 08 13:33:09 EST 2010
First of all thanks to everyone...

Sudarshan, your suggestion was very helpful to me. My dxl is now checking the latest history session and writing the modify, delete and create object records to a text file. It has failed once but I could not find the reason, I am searching for it. The only problem left is, I did not want the records of modifying the other attributes (just need the object heading and text but they are also written as "modifyObject" type of history to the text file. I thought their history type was "modifyAttr", but I guess I was wrong. I will be working on that.

Roy, your suggestion is also worth trying I think, the problem is there are other users, and I can not control if they set show-> deletions checked all the time. My main reason for writing this dxl is to write the modified/deleted/created objects to a file when other users change a module and e-mail them to me.

You all have been vey helpful, thanks again.
Cigdem

roybond - Mon Jan 11 04:04:58 EST 2010
Louie,

Ok. The information I gave was simply to let 'cidem' know that to trigger off the deletion of an object is possible, and to give him the basics off what is required, to get him started.

My own implementation is far more complex, and does not actually (now) use a trigger, and is a combination of a predefined Default View with 'Show Deletions' set, and a Layout DXL column in place of the ID column which serves to display the Object ID under certain circumstances, but also performs other tasks such as monitoring for Object Deletion by the User.

Our Schema is such that we do not allow for Object Deletion when the Object (Requirement) has also passed through a particular State in its lifecycle, which is why I then Undelete the Object, and then set its Status to indicate a Deletion was requested.

Now, as I said - my own solution is far more complicated, but my original implementation stemmed from a simple Object DXL Attribute which then fired a Trigger.

Roy.

cidem - Fri Jan 08 13:33:09 EST 2010
First of all thanks to everyone...

Sudarshan, your suggestion was very helpful to me. My dxl is now checking the latest history session and writing the modify, delete and create object records to a text file. It has failed once but I could not find the reason, I am searching for it. The only problem left is, I did not want the records of modifying the other attributes (just need the object heading and text but they are also written as "modifyObject" type of history to the text file. I thought their history type was "modifyAttr", but I guess I was wrong. I will be working on that.

Roy, your suggestion is also worth trying I think, the problem is there are other users, and I can not control if they set show-> deletions checked all the time. My main reason for writing this dxl is to write the modified/deleted/created objects to a file when other users change a module and e-mail them to me.

You all have been vey helpful, thanks again.
Cigdem

SudarshanRao - Mon Jan 11 11:29:28 EST 2010
@cidem,
Yes, modifyObject will be for modification of any attributes' value. You can identify the attribute using the property "attrName". In the sample I used earlier, having an if condition - if(h.type == "modifyObject" && ((h.attrName == "Object Heading") || (h.attrName == "Object Text"))) - once session is validated, should help I guess..
modifyAttr is for modification of attribute definition.